Release 10.1A: OpenEdge Getting Started:
Database Essentials

Mapping objects to areas

Creating optimal storage areas and proper relationships between areas and objects will enhance your database performance. You can define one object per area, or have multiple objects in an area. Use the information in Table 3–2 to guide your design decision.

Table 3–2: Guidelines for storage areas

If your database contains. . .	Then you should. . .
Many large or frequently updated tables.	Create a storage area for each table. This will give you easier administration and better performance.
Many small tables.	Create storage areas to represent a distinct subject (for example Sales, Inventory, etc.) and assign related tables to that storage area. This will give you easier administration.
A mixture of large and small tables.	Combine the above two strategies.
Many indexes for large or frequently updated tables.	Create a storage area for each index. This will give you flexibility in administration and the potential for better performance.
Many of small indexes.	Create storage areas representing a distinct subject for these indexes. This will give you easier administration.